ARC breaks occur when a person in charge requests something be looked into and he is given an opinion or an explanation.

It is not a true comm cycle.

An Esto has a definite job to do. He is not part of the division’s lines. He hats, organizes, trains, sets up files, lines, and does all those establishment actions people need to really establish a division and maintain it.

“Go see what’s smoking.”

If you want an Esto to go into gales of laughter, say “I am too busy to get hatted.” Those papers and that enmest show that a 2 hours of hatting a day save a year of dev-t nonproduction.

“I think it’s George burning toast.”

HCO over the world could not establish orgs. It can do its departmental functions. The answer is the Esto.

“Put out a bow line.”

You’ll be seeing a lot of this. Might as well know who these strange people are who keep insisting you find out about comm baskets and things.

“We’ve got one out.” (When a second one is needed.)

Gives one a long string of non-comm cycles and is a sure-fire ARC break.

I think this is why those in charge get upset. Getting an opinion or explanation when an order is meant to be done.

Part of the fault is not wording the order in anticipation of such a reply.

[Note: The original mimeo copies of this policy letter were incorrectly numbered as Exec Series 21.]